fix(code): don't include timestamp overlay when copying user messages#1941
Merged
VojtechBartos merged 1 commit intomainfrom Apr 29, 2026
Merged
Conversation
Selecting a one-line user message and copying it pulled in the hover timestamp text. Marking the overlay non-selectable keeps copies clean without affecting the copy button click handler. Generated-By: PostHog Code Task-Id: a49fe873-8e2a-4fea-8db6-725ab0c4498b
Contributor
|
Reviews (1): Last reviewed commit: "fix(code): exclude user message timestam..." | Re-trigger Greptile |
joshsny
approved these changes
Apr 29, 2026
VojtechBartos
deleted the
posthog-code/investigate-message-date-time-copy-issue
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Selecting a one-line user message used to drag the hover timestamp into the copy. Marking the overlay
select-nonekeeps copies clean; the copy button still works.Fixes feedback from this Slack thread.
Created with PostHog Code